User-Centred Requirements Handbook |
Having developed a range of ideas for the new system, an assessment is made as to whether the design ideas and concepts form a sufficiently good basis for further development as a prototype.
If so, then the process continues with Phase 2.
If not, then return to 1.10 to consider new ideas that may be included in the system.
Phase 2
Prototype and User test
Phase 2 of the user requirements specification process consists of the second iteration around the user-centred design loop as shown below.
• Context: The first part of phase 2 is to identify task scenarios that will be used as a way of testing the system design. At least one scenario is produced for each user goal. Each scenario represents a user goal set within a particular context. Usability goals to be achieved for each scenario are also produced.
• Requirements: For each scenario, a set of steps representing an interactive process is developed. At the same time, a list of potential functions of features to support that process is also documented.
• Design: Here an interactive prototype of the system is produced, based on the list of functions and features defined. This will be used to test the system concept against the scenarios with potential users.
• Test: Here the prototype is used to carry out the different scenarios with users. Any problems are then documented. A review is carried out of the tasks that each user will carry out for all user goals. The acceptability of each group tasks for that user group is considered. If both the prototype is satisfactory and the user task groupings are acceptable, the process may move on to the documentation of user requirements in Phase 3.
Figure 8. Phase 2 - Prototyping and user testing